fix - critical error when destructuring widget props#25
Merged
Conversation
Jhvictor4
force-pushed
the
fix/fix-use-widget-props
branch
from
d3857d3 to
31d66fe
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It seems that widgets using
useWidgetProps()had not been rendered properly, since the app expects the method to return the return value of theexecutefunction of Python MCP server's widget, while it actually just returnswindow.openai.toolOutputwhich wraps out the result ofexecutefunction, including the value aswindow.openai.toolOutput.structuredContent.It seems that the npm registry might be properly fixed, but in advance, destructuring
useWidgetPropsoutput seems okay for now.